Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BIOMAGE-2001] Fix gene selection error and reload #780

Merged
merged 2 commits into from
Jul 25, 2022

Conversation

jszpila314
Copy link
Contributor

@jszpila314 jszpila314 commented Jul 25, 2022

Description

If plot data fails to load, plotData is undefined and an error is thrown when selected genes are re-ordered or deleted. Add checks to skip if 'plotData' is undefined.
When exiting to data-management and returning to the dot plot, check to skip loading initial genes as selected genes was not working correctly, because it was triggered while data was loading.

Details

URL to issue

https://biomage.atlassian.net/browse/BIOMAGE-2001

Link to staging deployment URL (or set N/A)

N/A

Links to any PRs or resources related to this PR

#759

Integration test branch

master

Merge checklist

Your changes will be ready for merging after all of the steps below have been completed.

Code updates

Have best practices and ongoing refactors being observed in this PR

  • Migrated any selector / reducer used to the new format.

Manual/unit testing

  • Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
  • Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
  • Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing

You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

  • Started end-to-end tests on the latest commit.

Documentation updates

  • Relevant Github READMEs updated or no GitHub README updates required.
  • Relevant Wiki pages created/updated or no Wiki updates required.

Optional

  • Staging environment is unstaged before merging.
  • Photo of a cute animal attached to this PR.

@codecov
Copy link

codecov bot commented Jul 25, 2022

Codecov Report

Merging #780 (f0ed066) into master (c45177e) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #780   +/-   ##
=======================================
  Coverage   83.85%   83.85%           
=======================================
  Files         473      473           
  Lines        8064     8066    +2     
  Branches     1564     1566    +2     
=======================================
+ Hits         6762     6764    +2     
  Misses       1244     1244           
  Partials       58       58           
Impacted Files Coverage Δ
...[experimentId]/plots-and-tables/dot-plot/index.jsx 94.52% <100.00%> (+0.07%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us.

@github-actions
Copy link
Contributor

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/experiments/[experimentId]/plots-and-tables/dot-plot 496.96 KB (🟡 +3 B) 1019.33 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

@@ -190,6 +192,8 @@ const DotPlotPage = (props) => {
};

const deleteData = (genes) => {
if (!plotData) return;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this even be executed if theres no plotData - nothing to delete right? So maybe this is redundant?

Copy link
Contributor Author

@jszpila314 jszpila314 Jul 25, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This executes when returning to the dot plot when there is an error loading the plot data, due to for example the work request timing out. I ran into this due to some problems with the worker in staging, where the plot data wouldn't load and editing the tree threw errors.

@jszpila314 jszpila314 merged commit 525ab00 into master Jul 25, 2022
@jszpila314 jszpila314 deleted the fix-gene-selection-error-and-reload branch July 25, 2022 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants